After seting 3.7 the default (apache#19317) the warning printed by
Python during importing all providers (specifically apache beam)
has slightly changed. Apparently collections.abc warning was
a bit more "scary" - warning that it's 3.9 not 3.10 where the
old collection imports will stop working (Note that actually
this did not happen even in 3.10, apparently)

This PR fixes the "known" warning message to match it but also
a separate PR (apache/beam#15850) was
opened to Beam to get rid of the warnings altogether.

Also seems 'dns` stopped generating this warning so I removed it
and in case warnings are generated, they are printed outside of
the folded group, so that it's immediately visible.

After seting 3.7 the default (#19317) the warning printed by
Python during importing all providers (specifically apache beam)
has slightly changed. Apparently collections.abc warning was
a bit more "scary" - warning that it's 3.9 not 3.10 where the
old collection imports will stop working (Note that actually
this did not happen even in 3.10, apparently)

This PR fixes the "known" warning message to match it but also
a separate PR (apache/beam#15850) was
opened to Beam to get rid of the warnings altogether.

Also seems 'dns` stopped generating this warning so I removed it
and in case warnings are generated, they are printed outside of
the folded group, so that it's immediately visible.

Continuation of #18922

This case was missed and is needed to have correct image tagged for Dockerfiles

(cherry picked from commit 98d9067)

This PR enables mypy back as pre-commit for local changes after
the apache#19317 switched to Python 3.7 but also it separates out
mypy to a separate non-failing step in CI.

In the CI we will be able to see remaining mypy errors.

This will allow us to gradually fix all the mypy errors and enable
mypy back when we got all the problems fixed.

In order to keep consistency, both mypy and flake were always
using Python 3.6 - simply to make sure that the same errors
are produced for everyone. When default python version was
changed in apache#19317 the regular PR static checks started to fail
because Python 3.6 image is no longer built for "regular" PRs
(it's only built when "full-tests-needed" is set or when
the build runs in "main" as result of push or schedule).

Unfortunately those "defaults" could not be read from
"default python version" easily, because they are also
executed in pre-commits, which do not have the same
initialization as `breeze` or other CI scripts so there
are literally 3 more places where Python 3.6 should be
changed to 3.7.

This PR fixes it.

This PR enables mypy back as pre-commit for local changes after
the #19317 switched to Python 3.7 but also it separates out
mypy to a separate non-failing step in CI.

In the CI we will be able to see remaining mypy errors.

This will allow us to gradually fix all the mypy errors and enable
mypy back when we got all the problems fixed.

After seting 3.7 the default (#19317) the warning printed by
Python during importing all providers (specifically apache beam)
has slightly changed. Apparently collections.abc warning was
a bit more "scary" - warning that it's 3.9 not 3.10 where the
old collection imports will stop working (Note that actually
this did not happen even in 3.10, apparently)

This PR fixes the "known" warning message to match it but also
a separate PR (apache/beam#15850) was
opened to Beam to get rid of the warnings altogether.

Also seems 'dns` stopped generating this warning so I removed it
and in case warnings are generated, they are printed outside of
the folded group, so that it's immediately visible.

(cherry picked from commit 4bb1317)

After seting 3.7 the default (#19317) the warning printed by
Python during importing all providers (specifically apache beam)
has slightly changed. Apparently collections.abc warning was
a bit more "scary" - warning that it's 3.9 not 3.10 where the
old collection imports will stop working (Note that actually
this did not happen even in 3.10, apparently)

This PR fixes the "known" warning message to match it but also
a separate PR (apache/beam#15850) was
opened to Beam to get rid of the warnings altogether.

Also seems 'dns` stopped generating this warning so I removed it
and in case warnings are generated, they are printed outside of
the folded group, so that it's immediately visible.

(cherry picked from commit 4bb1317)